Capturing the AWS Account ID during SQS Subscribe #24
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
This PR is the first step in fixing #25 with ListSubscriptions. When ListSubscriptions is invoked it should display ARNs for SQS subscriptions, however local-sns displays the endpoint instead. In order to fix this behavior we need to capture the AWS Account ID so that we can displays it as part of the ARN value. When an HTTP SQS endpoint subscription is created we need to capture this ID and set it as the
queueOwnerAWSAccountId
Camel parameter (see the docs.Changes
queueOwnerAWSAccountId
parameter when creating the AWS Camel-compliant endpoint. Example: For the SQS endpointhttps://sqs.us-east-1.amazonaws.com/123456789012/queue1
,123456789012
is the AWS Account ID.Testing and Validation Steps